Business Process Management Processor |
Settings
There are currently no settings defined for Business Process Management Processor type.
Counters
requestHandlingTimer
Counter type |
Event Value Counter |
Event |
Frequency of the request handling of this application connector |
Hints |
|
Alerts
dbConnectionFailure
Severity Level |
Error |
Message |
The database server may not be functioning, or the network may be encountering server connectivity problems. |
Description |
This alert is issued when processor cannot be started because of database connectivity problem. |
unableToResolveDso
Severity Level |
Error |
Message |
The process engine was not able to resolve the database configuration from the specified information in the business process model (transactional process: {0} for instance id: {1}.) |
Description |
This Alert is issued because of issues in resolving database configuration for transactional Process. |
stateSynchUpFailure
Severity Level |
Error |
Message |
State synch up (SSU) is not configured. State synch up is required to synchronization among multiple BPM Engines configured for load balancing. |
Description |
This Alert is issued because of State Synch up Configuration Problems. |
notificationSOAPProcessorFailure
Severity Level |
Error |
Message |
The system was not able to deliver the notification from the process engine. The Notification SOAP processor is not functioning properly, or has not yet been started. |
Description |
This Alert is issued because of Notification Soap Processor Failure. |
binaryParserInitializationFailure
Severity Level |
Error |
Message |
Embedded Binary Parser could not be initialized. Check the configuration details in the SOAP Processor Configuration. |
Description |
This Alert is issued because Embedded Binary Parser could not be initialized. |
ruleEngineInitializationFailure
Severity Level |
Error |
Message |
Embedded Rule Engine could not be initialized. Check the configuration details in the SOAP Processor Configuration. |
Description |
This Alert is issued because Embedded Rule Engine could not be initialized. |
reachedMaxIterationCountDesc
Severity Level |
Error |
Message |
The execution of business process-instance with instance-id {0} of business process model {1} running in organization {2} and started by user {3} is suspended by the system as the current iteration count {4} for the loop activity {5} with activity-type {6} reached the threshold limit {7} for execution of maximum number of iterations in a single run set by the administrator. In order to continue execution, the business process instance is required to be resumed manually by the administrator. |
Description |
The execution of business process-instance with instance-id {0} of business process model {1} running in organization {2} and started by user {3} is suspended by the system as the current iteration count {4} for the loop activity {5} with activity-type {6} reached the threshold limit {7} for execution of maximum number of iterations in a single run set by the administrator. In order to continue execution, the business process instance is required to be resumed manually by the administrator. |
archiveFileZippingFailure
Severity Level |
Error |
Message |
The archive file could not be created successfully. Please create a zip of the folder at {0} with the same folder name. |
Description |
This Alert is issued because the Archive File could not be created sucessfully due to zipping failure . |
reachedMaxAllowedInstanceCountDesc
Severity Level |
Error |
Message |
The current rate of creation of new process-instances {0} for the business process model {1} (deployed to model-space {2}) exceeded the threshold limit {3} process-instances per {4} second(s) set by the administrator. The request is sent from the organization {5} by user {6}. Try after some time or contact administrator. |
Description |
The current rate of creation of new process-instances {0} for the business process model {1} (deployed to model-space {2}) exceeded the threshold limit {3} process-instances per {4} second(s) set by the administrator. The request is sent from the organization {5} by user {6}. Try after some time or contact administrator. |
Problems
databaseConnectionFailure
problemRaiseDescription |
The database server is not available. The database server may not be functioning, or the network may be encountering server connectivity problems. Ensure that the database server is functioning, and the network is communicating properly with the server. |
problemClearDescription |
Connection to the database Server has been established. |
Sub-components
The Business Process Management Processor has five sub-components : Business Process Engine, Case Management Engine, Embedded Data Mapper, Process Engine Database Connection Pool and Scheduler DBConnectionPool